Providing a communications channel between instances of automated assistants

ABSTRACT

Implementations relate to interactions, over a wireless communication modality, between an automated assistant of an automobile computer system, and separate client device(s). In some of those implementations, the client device(s) can be paired with the automobile computer system, and the client device(s) and the automobile computer system can include separate instances of an automated assistant, which can be associated with different user accounts. In some additional or alternative implementations, particular actions to be performed by a local application of a client device can be advanced via user interaction with the automobile automated assistant, despite a counterpart to the local application not being installed directly on automobile computer system. For example, despite an automobile computer system not having a third-party messaging application installed, the automobile automated assistant can access requested actions to be performed by the third-party messaging application in order to further a requested action. The automobile computer system can transmit, via the wireless communication modality, content to cause the third-party application to further the requested action.

BACKGROUND

Humans may engage in human-to-computer dialogs with interactive softwareapplications referred to herein as “automated assistants” (also referredto as “digital agents,” “chatbots,” “interactive personal assistants,”“intelligent personal assistants,” “assistant applications,”“conversational agents,” etc.). For example, humans (which when theyinteract with automated assistants may be referred to as “users”) mayprovide commands and/or requests to an automated assistant using spokennatural language input (i.e. utterances), which may in some cases beconverted into text and then processed, and/or by providing textual(e.g., typed) natural language input.

Automated assistants can be installed at a variety of different devicessuch as, for example, mobile phones and personal computers. A user cancause a particular application at a mobile phone or a personal computerto perform a particular action by interacting with a respectiveautomated assistant. However, in order to exhibit uniformity offunctionality across different devices, a user may be required toinstall instances of the same application synchronously across thedifferent devices. As a result, network bandwidth may be quicklypreoccupied with transmitting duplicative application updates for eachinstance of the application and generally communicating data betweeneach instance of the application. Moreover, as each instance of theapplication may require some amount of disk space on their respectivedevice, memory allocation across devices may be employed inefficiently.

In some contexts, interacting with a particular application via anautomated assistant may not be convenient depending on how engaged auser may be in a particular environment, and/or whether other devicesare being operated by other users nearby. For instance, replying tomessages via an automated assistant on a mobile phone can be difficultwhile the user is driving in a vehicle. Furthermore, when the user isdriving with other people in the vehicle, those people may also havedevices with automated assistants, which may be indirectly invoked asthe user engages with their respective automated assistant. Such aresult can create an environment of heightened distractions whiledriving, and waste computational resources at those devices that may beinadvertently affected.

SUMMARY

Implementations set forth herein relate to systems, methods, andapparatuses for providing a communications channel through whichseparate instances or installations of automated assistants cancommunicate in order to further a particular action. The communicationschannel can be provided between a principal automated assistant (e.g.,either an automobile automated assistant or a client device automatedassistant) and one or more subsidiary automated assistants (e.g., theother of the automobile automated assistant and the client deviceautomated assistant). For instance, a principal automated assistant canbe one that is preferred by a user in a particular context, such asriding in an automobile. Specifically, an automobile computer system caninclude an automated assistant that is preferred by a user forfurthering particular actions while the user is riding in the vehicle.According to settings of the automobile and/or a client device, theautomobile automated assistant, as principal, can assume any pendingintents and/or actions of a subsidiary automated assistant when theclient device connects to the automobile computer system. In this way,the automobile automated assistant can act as an extension of thesubsidiary automated assistant. This can allow any client-sideapplications to tunnel or channel particular intents and/or actions toand/or from the automobile automated assistant. Furthermore, suchtunneling can provide a system architecture that supports an ability ofthe user to engage with their respective client-side applications,without necessarily employing or installing any correlated“automobile-side” applications at the automobile computer system. Inthis way, a more efficient use of automobile-side memory can beeffectuated through not necessarily requiring such correlated,third-party applications to be installed on every automobile-sidedevice. Furthermore, network traffic and wasteful power consumptionwould be mitigated as a result of the user merely relying on theirautomated assistants to communicate with at least a single instance ofan application, rather than employing multiple instances of multipleapplications to synchronously operate. In particular, a reduction innetwork and computational resources can be exhibited by messagingservers and applications that would otherwise send duplicative copies ofmessages and confirmation receipts to a variety of different devices.

For instance, in some implementations, an automobile automated assistantof a vehicle can be employed to communicate a message received at athird-party application of a client device, such as a mobile phone, andrespond to the message according to an interaction between a user andthe automobile automated assistant. In order to achieve suchfunctionality, the client device and an automobile computer system ofthe automobile can perform a handshake, in order to establish a securecommunication channel between the client device and the automobilecomputer system. Specifically, the client device can assign one or morenetwork sockets (e.g., a Bluetooth socket(s)) as nodes for transmittingdata to and/or from the automobile computer system. When a securecommunication channel has been established between the client device andthe automobile computer system, action intents can be shared between theclient automated assistant and the automobile automated assistant.

An action intent can refer to a request from an application, for aparticular action to be performed via the application or a separateapplication. For instance, an action intent request can be generated bya third-party application and identify one or more of an action to beperformed, a custom identifier, content data that is associated with theaction to be performed, and/or any other data that can be associatedwith an action to be performed by an application. The action intent canbe initially received by an operating system, device application,automated assistant, and/or any other engine or module available of thedevice at which the action intent was originated. The action intent canthen be cataloged, or otherwise queued, at the originating device, andmade accessible to one or more instances of the automated assistant. Forexample, a client automated assistant of the originating client devicecan access the pending action intent, and, when the client device ispaired with an automobile computer system, an automobile automatedassistant can access the pending action intent.

In furtherance of the aforementioned example, the automobile automatedassistant can communicate with the client automated assistant toidentify a pending action intent request. The action intent request canbe associated with a message that was received at a third-partyapplication of the client device while the user was riding in theautomobile. The term “third party” can refer to an entity that createdand/or provided the third-party application, and is different than acreator and/or provider of the client device, the client automatedassistant, and/or a client operating system. By accessing the actionintent request at the client device, the automobile automated assistantcan act as an intermediary through which the user can further particularpending action intent requests. Furthermore, the automobile automatedassistant can cause a corresponding instance of the action intentrequest, as well as any other action intent requests that might bepending at the client device, to be generated at the automobile computersystem. The corresponding instances of the action intent requests at theautomobile computer system can be handled by the automobile automatedassistant, despite the automobile computer system being void of thethird-party application that originated the message.

The automobile automated assistant can determine that the action intentrequest is associated with a message based on the content of the actionintent request, and, in some implementations, regardless of thethird-party application that provided the action intent request. In thisway, the automated assistant can manage action intents from a variety ofdifferent applications, seemingly agnostic with respect to theapplications that are originating the action intents. For instance, afirst service provider of a first application and a second serviceprovider of a second application can each provide messages in differentmanners, however, the respective messages will have a “body” and a“sender” field regardless. The overlap in the structure of messages,which, in some implementations can be in part due to a respectiveapplication satisfying an API, can allow each message to be similarlyparsed. An automated assistant can then use any parsed data from arespective message to provide notifications, respond to message, and/orperform any other action that can be associated with a message. In someimplementations, similar overlaps can be exhibited by other applicationscapable of interacting with an automated assistant. Such otherapplications can include navigation applications, where contents of anotification can include route steps, and/or media applications, wherecontents of a notification can include an address of particular mediadata, such as an image and/or a video.

When the automobile automated assistant determines that thecorresponding instance of the action intent request is associated with amessage, the automobile automated assistant can cause the contents ofthe corresponding instance to be parsed. The parsed contents can be usedto identify separate portions of the message, such as the body, theauthor, the subject, a sent and/or received time, and/or any other datathat can be associated with a message. Because the automobile automatedassistant has determined that the action intent request corresponds to amessage, the automobile automated assistant can use the parsed contentsin order to present the parsed contents to the user. For instance, theautomobile automated assistant can employ a text-to-speech engine forconverting at least a portion of the content of the action intentrequest into audio that can be output from an automated assistantinterface, such as an audio system, of the automobile computer system.The audio can be, for example, “You received a text message from‘Emily,’ which she says, ‘I will be running late.’” The author “Emily”and the body “I will be running late” can be based on data that wasparsed from the corresponding instance of the action intent request.

In response to notifying the user of the message received at theirclient device, the automobile automated assistant can follow up with aprompt, which can present the user with the option to reply to themessage. The prompt can include responsive audio such as, “Would youlike to reply to ‘Emily’?” and, in response, the user can provide aspoken utterance such as, for example, “Yes, please respond, ‘Okay.’”Accordingly, the automobile automated assistant can receive the spokenutterance, via the automated assistant interface of the automobile, andemploy a speech-to-text engine accessible to the automobile computersystem to process the spoken utterance. The text derived from the spokenutterance can be embodied as content that can be part of a subsequentaction intent request that is generated by the automobile automatedassistant. The subsequent action intent request can be further generatedto identify an action, such as sending a message, which should beperformed by a target application (e.g., the third-party application).

In order to synchronize the subsequent action intent with the actionintent request generated by the client device, the automobile automatedassistant can generate the subsequent action intent using the samecustom identifier as the action intent request generated by the clientdevice. In this way, the client device can access the subsequent actionintent request and/or determine that the subsequent action intentrequest was generated at the automobile computer system, and determine acorrelation between the subsequent action intent request and the actionintent request. In some implementations, the custom identifier can beused as at least one key for encrypting transmissions between theautomated assistants.

When the subsequent action intent request has been generated at theautomobile computer system, the client automated assistant can determinethat the subsequent action intent request was generated, and generate acorresponding instance of the subsequent action intent request at theclient device. Because the subsequent action intent request is directedat sending a message via the third-party application, the clientautomated assistant and/or client device can invoke the third-partyapplication to send the message. In other words, because automobilecomputer system does not include an instance of the third-partyapplication, the generation of the subsequent action intent request doesnot directly invoke any instance of the third-party applicationinstalled at the automobile computer system. Rather, in response to theclient automated assistant acknowledging the generation of thesubsequent action intent request and/or the corresponding instance ofthe subsequent action intent request being generated at the clientdevice, the third-party application performs the sending of theresponsive message.

In some implementations, in response to the user acknowledging thereceipt of the message and/or in response the user indicating they wouldlike to respond to the message, a pendency of the action intent requestat the client device and the automobile computer system can bedismissed. For instance, in response to the user providing the spokenutterance, “Yes, please respond, ‘Okay,’” the automobile automatedassistant can cause a corresponding instance of the action intentrequest to be dismissed at the automobile computer system. Additionally,in response to the user providing the aforementioned spoken utterance,the client automated assistant can cause the action intent request to bedismissed at the client device. If a separate corresponding instance ofthe action intent request associated with the originally receivedmessage is available at, for example, a remote server device, theseparate corresponding instance can also be dismissed.

The above description is provided as an overview of some implementationsof the present disclosure. Further description of those implementations,and other implementations, are described in more detail below.

In some implementations, a method implemented by one or more processorsis set forth as including operations such as identifying, by anautomobile automated assistant, a first action intent request that isgenerated at a client device. The client device can be paired with anautomobile computer system via a wireless communication channel, whereinthe automobile computer system includes the automobile automatedassistant. The operations can also include determining, in response toidentifying the first action intent request, that the first actionintent request identifies: a first requested action to be performed,content data to be accessed for performing the requested action, and anidentifier that is associated with an application that at leastpartially caused the first action intent request to be available to theautomobile computer system. The operations can also include causing, infurtherance of the first requested action to be performed, an automatedassistant interface accessible to the automobile computer system toprovide an output to a user of the automobile computer system, whereinthe output is based on the content data of the first action intentrequest. The operations can further include determining, by theautomobile automated assistant, that the user provided an input inresponse to the output provided at the automated assistant interface;and providing, in response to determining that the user provided theinput, a second action intent request to the client device. The secondaction intent request can identify: a second requested action to beperformed at the client device, other content data that is based on theinput provided by the user, and the identifier. The operations can alsoinclude causing the second requested action to be performed at theclient device according to the second action intent request. The secondrequested action can be performed by the application using the othercontent data, and the application can be identified by the client deviceusing the identifier provided in the second action intent request.

In some implementations, the method can include providing, in responseto determining that the user provided the input, a third action intentrequest to the client device, the third action intent requestidentifying the identifier and a third requested action, wherein, inresponse to the client device receiving the third action intent request,the third action intent request causes a pendency of the second actionintent request at the client device to be dismissed. In someimplementations, the method can include causing, in response todetermining that the user provided the input, a dismissal of a separatependency of a corresponding instance of the second action intentrequest, wherein the corresponding instance of the second action intentrequest is provided at the automobile computer system. In someimplementations, the pendency of the second action intent request isindicated by a first automated assistant event handler accessible viathe client device, and the separate pendency of the correspondinginstance of the second action intent request is indicated by a secondautomated assistant event handler accessible via the automobile computersystem.

In some implementations, the automobile computer system is void of aninstalled application that: (i) is provided by a third party whoprovided the application at the client device, and (ii) is at leastpartially correlated to the application at the client device. In someimplementations, the automobile computer system is paired with aseparate client device that includes another application that isprovided by a different third party relative to the application at theclient device, and the method further comprises: identifying, by theautomobile automated assistant, a separate action intent request that isgenerated at the separate client device, the separate client devicebeing paired with the automobile computer system. In someimplementations, the separate action intent request includes anotheridentifier generated by the separate client device, and the methodfurther comprises: designating, based on a difference between theidentifier and the other identifier, the first action intent request asa priority over the separate action intent request.

In other implementations, a method implemented by one or more processorsis set forth as including operations such as connecting, using anautomobile computer system, with a first client device via a wirelesscommunication modality, the first client device comprising a clientautomated assistant, and the automobile computer system comprising anautomobile automated assistant and an automobile sensor application, theautomobile sensor application configured to monitor at least one sensorof the automobile computer system. The method can also includeconnecting, using an automobile computer system, with a second clientdevice via the wireless communication modality, the second client devicecomprising another client automated assistant. The method can furtherinclude determining, by the automobile computer system, that a firstaction intent request was generated at the first client device by anapplication, wherein the application corresponds to a particularcategory of service and is provided by a first service provider. Themethod can also include determining, by the automobile computer system,that a second action intent request was generated at the second clientdevice by another application, wherein the other application correspondsto the particular category of service and is provided by a secondservice provider. The method can further include determining, using theautomobile computer system, that a third action intent request wasgenerated at the automobile sensor application, wherein the third actionintent request is generated based on sensor data from the sensor of theautomobile computer system. The method can also include generating, bythe automobile automated assistant, data indicating a pendency of eachaction intent request of the first action intent request, the secondaction intent request, and the third action intent request, wherein thedata is stored at the automobile computer system. The method can furtherinclude causing, according to the generated data, one or more interfacesconnected to the automobile computer system to provide a notificationfor each action intent request of the first action intent request, thesecond action intent request, and the third action intent request.

In some implementations, the method can include causing, in response todetermining that the third action intent request was generated at theautomobile sensor application, a corresponding instance of the thirdaction intent request to be stored at the first client device. In someimplementations, the method can include receiving a user input at theone or more interfaces connected to the automobile computer system; andcausing, in response to receiving the user input, a pendency of thenotification associated with the third action intent request to bedismissed at the automobile computer system and the correspondinginstance of the third action intent request to be dismissed at the firstclient device. In some implementations, the particular category ofservice is a messaging service and the first service provider isdifferent than the second service provider. In some implementations, themethod can include processing, for each action intent request of thefirst action intent request and the second action intent request,content of each message embodied by each action intent request, whereinthe processing of the content of each message is performed inattentiveof whether each message was provided by a service provider of the firstservice provider and the second service provider. In someimplementations, generating the data indicating the pendency of eachaction intent request includes: generating, by the automobile automatedassistant, a corresponding instance of each action intent request of thefirst action intent request, the second action intent request, and thethird action intent request.

In yet other implementations, a method implemented by one or moreprocessors is set forth as including operations such as connecting, by aclient device via a wireless modality, with an automobile computersystem that is integral to a vehicle and includes an automobileautomated assistant, wherein the client device includes a clientautomated assistant. The method can also include accessing, by theclient device via the automobile computer system, an action intentrequest that was received by the automobile automated assistant from anapplication of the automobile computer system, wherein the applicationis in communication with a sensor of the vehicle and the action intentrequest is based at least on a signal from the sensor. The method canfurther include generating, by the client automated assistant and basedon accessing the action intent request, a corresponding instance of theaction intent request, wherein the client device includes one or moreother action intent requests provided by one or more other applicationsat the client device. The method can also include disconnecting theclient device from the automobile computer system, at least based on theclient device becoming less proximate to the vehicle or the automobilecomputer system. The method can further include performing, by theclient automated assistant subsequent to disconnecting from theautomobile computer system, an action according to the correspondinginstance of the action intent request, wherein performing the actionincludes providing, at an interface of the client device, contentidentified by the action intent request.

In some implementations, the client device is void of an installedapplication that: (i) is provided by a third party who provided theapplication at the automobile computer system, and (ii) is at leastpartially correlated to the application at the automobile computersystem. In some implementations, determining a particular context, andperforming is in response to determining the particular context. In someimplementations, determining the particular context includes determininga location of the client device, and the method further comprises:determining that the content identified by the action intent request isassociated with the location of the client device, wherein the action isperformed in response to determining that the content identified by theaction intent request is associated with the location of the clientdevice. In some implementations, the method can include providing, basedon the client automated assistant performing the action according to thecorresponding instance of the action intent request, a request for theaction intent request to be dismissed at the automobile computer system.In some implementations, the request is provided to a remote serverdevice that is configured to communicate with the automobile computersystem and cause the action intent request to be dismissed at theautomobile computer system. In some implementations, the action intentrequest was generated in response to a user providing a spoken utteranceto an automated assistant interface of the automobile computer system,and wherein the method further comprises: receiving, from the automobilecomputer system in response to the user providing the spoken utteranceto the automated assistant interface, data corresponding to the spokenutterance; and providing, to the automobile computer system, responsivedata based on the data received from the automobile computer system,wherein the action intent request is further based on the responsivedata received by the automobile computer system.

Other implementations may include a non-transitory computer readablestorage medium storing instructions executable by one or more processors(e.g., central processing unit(s) (CPU(s)), graphics processing unit(s)(GPU(s)), and/or tensor processing unit(s) (TPU(s)) to perform a methodsuch as one or more of the methods described above and/or elsewhereherein. Yet other implementations may include a system of one or morecomputers and/or one or more robots that include one or more processorsoperable to execute stored instructions to perform a method such as oneor more of the methods described above and/or elsewhere herein.

It should be appreciated that all combinations of the foregoing conceptsand additional concepts described in greater detail herein arecontemplated as being part of the subject matter disclosed herein. Forexample, all combinations of claimed subject matter appearing at the endof this disclosure are contemplated as being part of the subject matterdisclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a perspective view of a vehicle that can allowmultiple different users to cause a vehicle automated assistant tointeract with applications at each of their respective devices.

FIG. 2 illustrates a system for providing an automated assistant that iscapable of interacting with other automated assistants in order tofurther actions requested by third party applications.

FIGS. 3A, 3B, and 3C illustrate perspective views of a scenario whereclient automated assistant of a portable computing device can act as aprimary or principal automated assistant for multiple instances of theautomated assistant.

FIGS. 4A and 4B illustrate methods for handling action intent requestsgenerated when a client device is in communication with an automobilecomputer system.

FIG. 5 illustrates a method of providing an output from an interfaceaccording to multiple different action intent requests provided fromdifferent instances of an automated assistant.

FIG. 6 is a block diagram of an example computer system.

DETAILED DESCRIPTION

FIG. 1 illustrates a perspective view 100 of a vehicle 114 that canallow multiple different users to cause a vehicle automated assistant tointeract with applications at each of their respective devices. Whenriding in a vehicle 114, a first user 110 and a second user 112 maybring different devices to interact with during their excursion in thevehicle 114. For instance, the first user 110 can bring a cellulardevice 124 (i.e., a client device) and the second user 112 can bring atablet device 116 (i.e., a client device). The vehicle 114 can includean automobile computer system 102, which can provide the users withaccess to an automobile automated assistant 104. Each of the cellulardevice 124 and the tablet device 116 can include a client automatedassistant 126 and a client automated assistant 118, respectively.Furthermore, the automobile automated assistant 104 can act as a primaryautomated assistant when each of the users bring their respectivedevices into the vehicle 114. In this way, each user does notnecessarily have to pair their respective device exclusively to theautomobile computer system 102. Furthermore, according to someimplementations of the automobile automated assistant 104, theautomobile computer system 102 does not necessarily need to have thesame applications that are installed on each of the client devices. Inthis way, the automobile computer system 102 can make a more efficientuse of memory, and, furthermore, with fewer installed applications, theautomobile computer system 102 would not consume as much networkbandwidth retrieving updates and communicating with servers. Suchbenefits can be realized, in part, through interactions between eachrespective automated assistant over a wireless communication modalityavailable at the vehicle 114. Furthermore, similar benefits can berealized at servers that would otherwise use phone numbers forauthenticating and delivering each message.

For example, each user can enter the vehicle 114 with their respectiveclient devices, and each client device can include and/or generateaction intent requests. For instance, the tablet device 116 can includeone or more tablet applications 120, capable of generating action intentrequests 122, and the cellular device 124 can include one or morecellular applications 128 capable of generating action intent requests130. The tablet applications 120 and/or the cellular applications 128can be third-party applications and/or applications that are provided ordeveloped by an entity that is different than an entity that provided ordeveloped one or more instances of the automated assistant.

When the first user 110 and the second user 112 initially enter theirvehicle 114 with their respective client devices, each client device candetermine that the vehicle 114 includes an automobile computer system102 capable of communicating over a wireless modality. Furthermore, eachclient device can determine that the automobile computer system 102includes an automobile automated assistant 104. Specifically, the clientautomated assistant 118 and the client automated assistant 126 candetermine that the automobile computer system 102 includes theautomobile automated assistant 104. In response to making thedetermination, the client automated assistant 118 can causecorresponding instances of the action intent requests 122 to begenerated at the automobile computer system 102, and the clientautomated assistant 126 can cause corresponding instances of the actionintent requests 122, 130 to be generated at the automobile computersystem 102. As a result, the automobile automated assistant 104 cancause any actions associated with the corresponding instances of theaction intent requests (stored locally as action intent requests 108) tobe furthered via interactions between one or more users and theautomobile automated assistant 104. Moreover, the automobile automatedassistant 104 can further the actions identified by the action intentrequests 108 despite the automobile computer system 102 includingautomobile applications 106, which may not be equivalent to, orotherwise be an instance of, any one application of the tabletapplications 120 and/or the cellular applications 128. For instance, theautomobile applications 106 can include a maintenance application thatprovides the automobile automated assistant 104 with information aboutthe vehicle 114. The information can be shared with one or more both ofthe tablet device 116 and cellular device 124, despite either device notincluding an equivalent, or instance of, the maintenance application.This can allow each user to not necessarily direct their attention totheir devices during their excursion, but, rather, rely on theautomobile automated assistant 104 to relay their respectivenotifications and/or further any particular action.

FIG. 2 illustrates a system 200 for providing an automated assistantthat is capable of interacting with other automated assistants in orderto further actions requested by third party applications. An automatedassistant 204 can operate as part of an assistant application that isprovided at one or more computing devices, such as a first client device216 (e.g., a cellular phone 242), a second client device 218 (e.g., atablet device 244), and/or a remote computing device 202, such as aserver device 230. A user can interact with the automated assistant(s)204 via an assistant interface (e.g., inside a vehicle 240), which canbe a microphone, a camera, a touch screen display, a user interface,and/or any other apparatus capable of providing an interface between auser and an application. For instance, a user can initialize theautomated assistant 204 by providing a verbal, textual, and/or agraphical input to the assistant interface to cause the automatedassistant 204 to perform a function (e.g., provide data, control aperipheral device, access an agent, etc.). The first client device 216can include a display device, which can be a display panel that includesa touch interface for receiving touch inputs and/or gestures forallowing a user to cellular applications 250 of the first client device216 via the touch interface. The second client device 218 can alsoinclude a display device, which can be a display panel that includes atouch interface for receiving touch inputs and/or gestures for allowinga user to control cellular applications 254 of the second client device218 via the touch interface. In some implementations, the second clientdevice 218 can lack a display device, thereby providing an audible userinterface output, without providing a graphical user interface output.Furthermore, the second client device 218 can provide a user interface,such as a microphone, for receiving spoken natural language inputs froma user.

The first client device 216 and the second client device 218 can be incommunication with the remote computing device 202 over a network 214,such as the internet. The first client device 216 and the second clientdevice 218 can offload computational tasks to the remote computingdevice 202 in order to conserve computational resources at each of thefirst client device 216 and the second client device 218. For instance,the remote computing device 202 can host the automated assistant 204,and the first client device 216 and/or the second client device 218 cantransmit inputs received at one or more assistant interfaces to theremote computing device 202. However, in some implementations, theautomated assistant 204 can be hosted at the first client device 216and/or the second client device 218. In various implementations, all orless than all aspects of the automated assistant 204 can be implementedon the first client device 216 and/or the second client device 218. Insome of those implementations, aspects of the automated assistant 204are implemented via a local assistant application of the first clientdevice 216 or the second client device 218 and interface with the remotecomputing device 202 that implements other aspects of the automatedassistant 204. The remote computing device 202 can optionally serve aplurality of users and their associated assistant applications viamultiple threads. In some implementations where all or less than allaspects of the automated assistant 204 are implemented via a clientautomated assistant 226 of the first client device 216 or a clientautomated assistant 226 of the second client device 218, the clientautomated assistant can be an application that is separate from anoperating system of the first client device 216 and/or the second clientdevice 218 (e.g., installed “on top” of the operating system)—or canalternatively be implemented directly by the operating system of thefirst client device 216 or the second client device 218 (e.g.,considered an application of, but integral with, the operating system).

In some implementations, the remote computing device 202 can include avoice to text engine 216 that can process audio data received at anassistant interface to identify the text embodied in the audio data. Theprocess for converting the audio data to text can include a speechrecognition algorithm, which can employ neural networks, word2vecalgorithms, and/or statistical models for identifying groups of audiodata corresponding to words or phrases. The text converted from theaudio data can parsed by a text parser engine 208 and made available tothe automated assistant 204 as textual data that can be used to generateand/or identify command phrases from the user and/or a third partyapplication.

In some implementations, the remote computing device 202 can include atext to voice engine 228 for converting textual data into audio data.For instance, in response to the automobile automated assistant 234identifying a pending action intent request 238 associated with areceived message, the automobile automated assistant 234 can causecontent corresponding to the message to be transmitted to the text tovoice engine 228. In response to receiving the content, the text tovoice engine 228 can convert the content into audio data, which can betransmitted back to the automobile automated assistant 234. Theautomobile automated assistant 234 can then cause the audio data to beoutput as an audio output from an audio interface (e.g., speaker(s)).Text can be converted to audio using a neural network(s), statisticalmodel(s), and/or any other apparatus or module through which textualdata can be converted to audio (e.g., audio corresponding naturallanguage output). In some implementations, each of the voice to textengine 216, the text to voice engine 228, and/or the text parser engine208 can be located at one or more client-side devices, such as theautomobile computer system 232, the first client device 216, and/or thesecond client device 218. In this way, a respective automated assistantwould not necessarily have to transmit data to a remote server forprocessing, but could rather process the data locally in order togenerate and/or interpret particular data for a user.

In some implementations, one or more of the engines, applications,and/or operations of the server device 230 can be provided and/orexecuted at the automobile computer system 232, the first client device216, and/or the second client device 218. For instance, in someimplementations, the automobile computer system 232 can include the textto voice engine 228 and/or the voice to text engine 216. Furthermore, insome implementations, any content received at the automobile automatedassistant 234, the client automated assistant 246, and/or the clientautomated assistant 248 can be transmitted to the server device 230 whenthere is a connection between a device that hosts the respectiveassistant and the server device 230. Alternatively, or additionally,when no connection is available between a respective device or system,and the server device 230, any content received can be exclusivelyprocessed at the respective device and/or shared with other local devicein order that the content can be processed in parallel. For instance,when the content corresponds to a message received at the second clientdevice 218 and transmitted to the automobile computer system 232, theautomobile computer system 232 can employ a local text to voice enginein order to generate audio that can be provided to a user while ridingin the vehicle.

In some implementations, each device or system that include one or moreapplications can also include one or more corresponding action intentgeneration engines. An action intent generation engine can be controlledby an application in order to cause certain actions to be performed bythe application, another application, and/or any other module accessibleto the application. For instance, the application can be a messagingapplication and the messaging application can receive an incomingmessage. In response to receiving the incoming message, the actionintent generation engine of the messaging application can generate anaction intent for providing a notification to the user via an automatedassistant. The action intent can identify the action to be performed(e.g., providing a notification), content of the received message, acustom identifier associated with the message, and/or any other datathat can be associated with the message.

In some implementations, each action intent generation engine and/orapplication can be associated with a declaration and/or manifest fileindicating types of actions capable of being performed by theapplication. For instance, a messaging application can include amanifest file indicating that the messaging application is capable of atleast receiving messages, notifying the user of messages, and/orresponding to messages. An operating system and/or an automatedassistant can access each manifest file on one or more devices in orderto determine whether particular applications can handle particularactions. In this way, for example, action intents generated at theautomobile computer system 232 can be provided to either the firstclient device 216 or the second client device 218 based on whether aparticular manifest file at one of the devices indicates there is anapplication at the device that can handle the action intents. If morethan one application can handle a particular action intent, theoriginating device and/or a separate device, can prompt the user toselect the device to handle the particular action intent (e.g., via agraphical user interface).

In some implementations, each action intent generation engine can alsogenerate and/or filter action intents according to a customer identifierthat is associated with each action intent of the action intents. Forinstance, when an action intent generation engine generates an actionintent at the direction of an application, the action intent generationengine can also generate a custom identifier. The custom identifier canbe generated based on an identifier for content to be used in performingthe action, an identifier representing the originating application, anidentifier for the recipient, an identifier for the originating user, anidentifier for a context of the action intent, and/or any otherinformation that can be used as a basis from which to generate anidentifier.

Each automated assistant and/or operating system can be configured toparse an action intent to identify content data, an intended action tobe performed, and/or a custom identifier. In some implementations, theautomated assistant can process each action intent seemingly agnosticwith respect to the originating application. For instance, despite thefirst client device 216 and the second client device 218 includingdifferent messaging applications, the automobile computer system 232 canretrieve action intent requests from either messaging applications andread the message to the user via an automated assistant interface of theautomobile computer system 232. For example, a message application atthe first client device 216 can generate an action intent request 252,and when the user enters the vehicle 240, the pending action intentrequest can be accessed by the automobile automated assistant 234. Theautomobile automated assistant 234 can then generate a correspondinginstance of the pending action intent request. Because the content dataprovided by the action intent request can include data such as “Hey,have you left yet?,” the automobile automated assistant 234 candetermine that content data corresponds to an incoming message.Therefore, because many different messaging applications will generateaction intents in a similar manner, the automobile automated assistant234 can act to present and respond to such action intents in a universalmanner, and/or relatively agnostic to the entity that provided thecorresponding messaging application (e.g., a first service provider, asecond service provider, etc.).

In some implementations, computational resources can be preserved byemploying a voice to text engine to process audio data corresponding tomultiple spoken utterances, rather than performing multiple turnsbetween a speech recognition engine and the automated assistant. Forinstance, a principal automated assistant can receive a command from auser such as, “Send a message to Robert.” In response, the principalautomated assistant can have a preconfigured response such as, “Ok,which messaging application would you like to use? Your firstapplication, second application, or your third application?” The usercan provide a response, such as “My first application,” and then dictatea message such as, “How's your day been?” In some implementations, theautomated assistant can confirm the messaging application to use andprompt the user whether they would like to send or change the message(e.g., “Ok, should I send the message or change the message?”). At thistime, the user may request that a different messaging application beselected. For instance, the user can reply, “Please send with the secondmessaging application instead of the first messaging application.” Inresponse, the automated assistant can then cause the message to betransmitted by the second messaging application. This can reduce anumber of turns between the user and the automated assistant, given thatthe processing of messages would not need to be tailored for eachindividual messaging application.

In some implementations, each automated assistant (e.g., the automobileautomated assistant 234) can access and/or manage an event handler thatincludes data corresponding to pending action intent requests. Asactions in furtherance of the pending action intent requests areperformed, each event handler for each automated assistant can beupdated. In some implementations, an event handler can include pendingaction intent request that correspond to the same event. For instance,multiple different actions can be associated with a received message.Therefore, when a user receives a text message at their first clientdevice 216, a corresponding messaging application can generate multipleaction intent requests for handling the received text message. When thefirst client device 216 pairs with the automobile computer system 232over a wireless modality, such as, but not limited to Bluetooth, Wi-Fi,LTE, etc., the automobile automated assistant 234 can generatecorresponding instances of the multiple action intent requests. Thecorresponding instances of the multiple action intent requests can bemanaged by an event handler of the automobile automated assistant 234,and can include some amount of data that associates the correspondinginstances of the multiple action intent requests with the text messagereceived at the first client device 216. For example, an action intentrequest identified by the event handler of the automobile automatedassistant 234 can correspond to an action to notify the user of the textmessage and prompt the user regarding whether they would like torespond. The automobile automated assistant 234 can execute both actionsrelated to the received text message, without having direct local accessto the messaging application that is installed at the first clientdevice 216.

FIGS. 3A, 3B, and 3C illustrate perspective views 300, 302, and 304 of ascenario where client automated assistant of a portable computing devicecan act as a primary automated assistant for multiple instances of theautomated assistant. For instance, while a user is in their home 318,malfunction can be detected at an automobile 316 that is associated withthe user. The issue can be, for example, that a rodent has chewedthrough a cable, such as a wire that connects to a brake sensor, of theautomobile 316 at night. Although an automobile computer system 306 ofthe automobile 316 can be operating in a standby mode, an automobileautomated assistant 308 can be responsive to the issue, and generate oneor more action intent requests 312 associated with the issue.Specifically, the automobile automated assistant 308 can generate anaction intent request 314 for displaying an automobile issuenotification (e.g., “brake sensor”) to the user, and another actionintent request 320 for prompting the user to schedule maintenance (e.g.,“schedule repair?”) to resolve the issue. Each action intent request canbe generated with the same custom identifier (e.g., “4KAJC92W”), whichcan be associated with the originating issue. Furthermore, each actionintent request can identify an action to be performed (e.g.,“notification,” and “schedule”).

FIG. 3B illustrates a perspective view 302 of user 322 that has enteredthe automobile 316 with their cellular device 328, which also includesan instance of the automated assistant, as the client automatedassistant 328. In some implementations, the automobile computer system306 can include automobile applications 310 that are not installeddirectly to the cellular device 328. Furthermore, in someimplementations, the cellular device 328 can include cellularapplications 332 that are not installed directly to the automobilecomputer system 306. Regardless, action intent requests can betransmitted between the automobile computer system 306 and the cellulardevice 328 over a wireless modality, and can be parsed by a respectiveautomated assistant.

For instance, the action intent requests 314 and 320 can be generated bya maintenance application of the automobile applications 310 andaccessed by the automobile automated assistant 308. When the user 322enters the vehicle with their cellular device 328, the automobilecomputer system 306 and the cellular device 328 can perform a handshake,in order to ensure that a secure communications channel 326 is providedbetween them. When a communications channel 326 has been established,the client automated assistant 330 can identify the pending actionintent requests 312 that are available at the automobile computer system306. Furthermore, the automobile computer system 306 can identify anyaction intent requests 334 that are available at the cellular device328. When the client automated assistant 330 determines that the actionintent requests 314 and 320 do not have any corresponding instances atthe cellular device 328, the client automated assistant 330 can causeinstances of the action intent requests 314 and 320 to be available atthe cellular device 328. The instances of the action intent requests 314and 320 at the cellular device 328 can include the same customidentifiers from the automobile computer system 306, thereby allowingupdates for a particular event (e.g., an issue with the brake sensordetected) to be compiled over time.

FIG. 3C illustrates a perspective view 304 of the user 322 in their home346 subsequent to the instance of the action intent requests 314 and 320being generated. Specifically, the user 322 can enter their home 346and, in response, the client automated assistant can attempt to completethe actions indicated by the action intent requests 314 and 320. Forinstance, the client automated assistant can cause a display interfaceof the cellular device 328 to present selectable elements 338 and 340,which can correspond to the action intent requests 314 and 320.Alternatively, the user 322 can provide a spoken utterance 336 to aninterface (e.g., a microphone) of the cellular device 328 in order tocause the client automated assistant to present any notificationsassociated with any pending action intent requests. For instance, theuser 322 can provide a spoken utterance 336 such as, “Assistant, show mepending notifications.” In response, the client automated assistantcause a nearby display panel to present notifications associated withthe action intent requests to the user 322.

If the user 322 selects either of the selectable elements 338 and 340, apendency of the action intent requests 314 and 320 can be dismissed ateach device that included an instance of the action intent requests 314and 320. For instance, instances of the action intent requests 314 and320 can be dismissed at the automobile computer system 306 and thecellular device 328. In some implementations, the action intent requests314 and 320 can be dismissed at the automobile computer system, when, inresponse to the user 322 selecting the selectable elements 338 and 340,data can be transmitted over a network 342 to a remote device 344. Theremote device 344 can thereafter be accessed by the automobile computersystem 306, which can update an event handler of the automobile computersystem 306 according to the data at the remote device 344.

FIGS. 4A and 4B illustrate methods 400 and 410 for handling actionintent requests generated when a client device is in communication withan automobile computer system. The methods 400 and 410 can be performedby one or more of a computing device, application, and/or any otherapparatus or module capable of communicating over a wireless connection.The method 400 can include an operation 402 of identifying, by anautomobile automated assistant, a first action intent request that wasgenerated at a client device. The client device can be paired with anautomobile computer system via wireless communication modality. Thefirst action intent request can be generated by an application at theclient device, for instance, in response to an operation (e.g.,receiving a message) performed at the application. In someimplementations, the automobile computer system can be void of acorresponding instance of the application of the client device.Specifically, the automobile computer system can be void of a separateapplication that is provided by a third party that provided theapplication at the client device, and/or is at least partiallycorrelated to the application at the client device. For instance, theapplication can be a text messaging application, and the automobilecomputer system can be void of the text messaging application.

The method 400 can further include an operation 404 of determining thatthe first action intent request identifies a first requested action tobe performed, content data, and a custom identifier. The first requestedaction can be a request to notify a user that an incoming message wasreceived at a messaging application installed at the client device. Thecontent data can identify some or all of the text provided in thereceived text message (e.g., “Are you on the way?”). Furthermore, thecustom identifier can be a string of data that can provide acorrespondence between the received text message and the first actionintent request, in order that any further action taken with the firstaction intent request can be subsequently associated with the receivedtext message.

The method 400 can also include an operation 406 of causing an automatedassistant interface, accessible to the automobile computer system, toprovide an output to a user of the automobile computer system. Forinstance, the output can be provided in response to the automobileautomated assistant determining that the first action intent requestcorresponds to an action of providing a notification. The notificationcan be presented at the automated assistant interface, which can be adisplay panel that is connected to the automobile computer system.Alternatively, the automated assistant interface can be a speaker thatis connected to the automobile computer system, and the notification canbe an audible audio output such as, “Matthew sent you a message thatsays, ‘Are you on the way?’”

The method 400 can further include an operation 408 of determining, bythe automobile automated assistant, that the user provided an input inresponse to the output provided at the automated assistant interface.For instance, the user can provide a responsive spoken utterance suchas, “Please response, ‘Yes, I'm on the way,’” to an automated assistantinterface (e.g., a microphone) of the automobile. The automobileautomated assistant can receive audio data corresponding to theresponsive spoken utterance, either cause the audio data to be processedlocally or transmit the audio data to a separate device for processing.By processing the audio data, the automobile automated assistant candetermine whether the user has acknowledged the notification of the textmessage, and any other action that the user would like to perform. Forexample, in response to receiving the responsive spoken utterance, theautomobile automated assistant can cause a second action intent requestto be generated.

The method 400 can proceed to method 410, as indicated by a continuationelement “A,” encircled at FIGS. 4A and 4B. The method 410 can include anoperation 412 of providing, to the client device and in response todetermining that the user provided the input, the second action intentrequest. The second action intent request can identify a secondrequested action, other content data, and/or the custom identifierassociated with the first action intent request. The second requestedaction can be request to respond to the text message that was receivedat the messaging application. The other content data can include textthat is based on the responsive spoken utterance (e.g.,“content-data=‘text:Yes, I'm on the way’”), and the custom identifiercan be the same custom identifier from the first action intent request.

The method 410 can further include an operation 414 of causing thesecond requested action to be performed at the client device by theapplication using the other content data. For instance, when the actionincludes transmitting a responsive message, the client device can usingthe content data in order to generate the responsive message andtransmit the responsive message to the person who initially sent thetext message to the client device. In order to identify the text messageand/or application that the second action intent request corresponds, aninstance of the automated assistant at the client device can compare thecustom identifier to the custom identifier provided with the firstaction intent request. Alternatively, or additionally, the automatedassistant can identify the messaging application based on whether themessaging application can perform the second requested action, asindicated by a manifest file of the messaging application. The automatedassistant at the client device can then cause the messaging applicationto perform the second requested action, and thereby send the textmessage corresponding to the responsive spoken utterance.

FIG. 5 illustrates a method 500 of providing an output from an interfaceaccording to multiple different action intent requests provided fromdifferent instances of an automated assistant. The method 500 can beperformed by one or more of a computing device, an application, and/orany other apparatus or module capable of interacting with an automatedassistant. The method 500 can include an operation 502 of connecting, byan automobile computer system and via a wireless communication modality,with a first client device that includes a client automated assistant.The first client device can be, for example, a portable computing devicesuch as a cell phone or tablet computer, and the automobile computersystem can be a computing device that is integral to a vehicle capableof delivering multiple passengers. Furthermore, the wireless modalitycan be one or more wireless communication protocols such as Bluetooth,Wi-Fi, LTE, and/or any other modality through which multiple computingdevices can interact.

The method 500 can further include an operation 504 of connecting, bythe automobile computer system, and via the wireless communicationmodality, with a second client device that includes another clientautomated assistant. The other client automated assistant can beprovided the same or different entity as the client automated assistant,and the second client device can be the same or different type of clientdevice as the first client device. For instance, the first client devicecan be owned by a driver of the automobile and the second client devicecan be owned by a passenger of the automobile. Furthermore, operation502 and operation 504 can be performed when the driver and the passengerof the automobile enter the automobile. In this way, an automobileautomated assistant will be able to interact with the client automatedassistant and the other client automated assistant when the driver andthe passenger are in the automobile.

The method 500 can further include an operation 506 of determining thata first action intent request was generated by an application at thefirst client device and that a second action intent request wasgenerated by another application at the second client device. The firstaction intent request can correspond to a request for a notification tobe presented to the driver, and the notification can provide informationabout a message that was received at the first client device. The secondaction intent request can correspond to a different request for adifferent notification to be presented to the passenger. The othernotification can provide different information about a different messagethat was received at the second client device.

The method 500 can also include an operation 508 of determining that athird action intent request was generated by a separate application atthe automobile computer system. The separate application can be, forexample, a maintenance application that monitors one or more sensors ofthe automobile. Furthermore, the first client device and the secondclient device can be void of any corresponding instance of themaintenance application. In some implementations, the third actionintent request can correspond to a request for a notification to beprovided to the driver regarding a condition of the car, such as an oilchange being overdue and/or brake fluid needing to be replaced.

The method 500 can also include an operation 510 of generating, at theautomobile computer system, data indicating a pendency of each actionintent request of the first action intent request, the second actionintent request, and the third action intent request. The data can beembodied as or accessible to an event handler engine capable ofarranging data corresponding to various different action intent requestsfrom various different applications and/or devices. For instance, thedata can identify a priority of each of the action intent requests. Apriority for an action intent request can be based on, for example,whether the action intent request was generated at a device thatincludes a primary automated assistant (i.e., an automated assistantthat at least more than one other automated assistants are communicatingwith). For instance, the primary automated assistant, when the driverand the passenger are riding in the automobile, can be the automobileautomated assistant because it is installed at the automobile computersystem of the automobile. A next priority can be given to action intentrequests that are provided by a device that is associated with thedriver of the vehicle, such as the first client device. Thereafter,other priorities can be assigned to action intent requests associatedwith passengers of the automobile.

The method 500 can further include an operation 512 of causing, based onthe generated data, one or more interfaces connected to the automobilecomputer system to provide a notification for each action intent requestof the first action intent request, the second action intent request,and/or the third action intent request. In some implementations, theautomobile computer system can include an interface, such as a displaypanel, at which graphical elements are presented, and one or more of thegraphical elements can correspond to either of the action intentrequests. Furthermore, the display panel can be a touch interfacethrough which a user can select a graphical element in order toacknowledge a notification and cause another action intent request to begenerated at the automobile computer system.

FIG. 6 is a block diagram of an example computer system 610. Computersystem 610 typically includes at least one processor 614 whichcommunicates with a number of peripheral devices via bus subsystem 612.These peripheral devices may include a storage subsystem 624, including,for example, a memory 625 and a file storage subsystem 626, userinterface output devices 620, user interface input devices 622, and anetwork interface subsystem 616. The input and output devices allow userinteraction with computer system 610. Network interface subsystem 616provides an interface to outside networks and is coupled tocorresponding interface devices in other computer systems.

User interface input devices 622 may include a keyboard, pointingdevices such as a mouse, trackball, touchpad, or graphics tablet, ascanner, a touchscreen incorporated into the display, audio inputdevices such as voice recognition systems, microphones, and/or othertypes of input devices. In general, use of the term “input device” isintended to include all possible types of devices and ways to inputinformation into computer system 610 or onto a communication network.

User interface output devices 620 may include a display subsystem, aprinter, a fax machine, or non-visual displays such as audio outputdevices. The display subsystem may include a cathode ray tube (CRT), aflat-panel device such as a liquid crystal display (LCD), a projectiondevice, or some other mechanism for creating a visible image. Thedisplay subsystem may also provide non-visual display such as via audiooutput devices. In general, use of the term “output device” is intendedto include all possible types of devices and ways to output informationfrom computer system 610 to the user or to another machine or computersystem.

Storage subsystem 624 stores programming and data constructs thatprovide the functionality of some or all of the modules describedherein. For example, the storage subsystem 624 may include the logic toperform selected aspects of method 400, method 500, and/or to implementone or more of an automobile automated assistant, an automobile computersystem, a client automated assistant, a client device, a remote device,a server device, a vehicle, and/or any other module or apparatusdiscussed herein.

These software modules are generally executed by processor 614 alone orin combination with other processors. Memory 625 used in the storagesubsystem 624 can include a number of memories including a main randomaccess memory (RAM) 630 for storage of instructions and data duringprogram execution and a read only memory (ROM) 632 in which fixedinstructions are stored. A file storage subsystem 626 can providepersistent storage for program and data files, and may include a harddisk drive, a floppy disk drive along with associated removable media, aCD-ROM drive, an optical drive, or removable media cartridges. Themodules implementing the functionality of certain implementations may bestored by file storage subsystem 626 in the storage subsystem 624, or inother machines accessible by the processor(s) 614.

Bus subsystem 612 provides a mechanism for letting the variouscomponents and subsystems of computer system 610 communicate with eachother as intended. Although bus subsystem 612 is shown schematically asa single bus, alternative implementations of the bus subsystem may usemultiple busses.

Computer system 610 can be of varying types including a workstation,server, computing cluster, blade server, server farm, or any other dataprocessing system or computing device. Due to the ever-changing natureof computers and networks, the description of computer system 610depicted in FIG. 6 is intended only as a specific example for purposesof illustrating some implementations. Many other configurations ofcomputer system 610 are possible having more or fewer components thanthe computer system depicted in FIG. 6.

In situations in which the systems described herein collect personalinformation about users (or as often referred to herein,“participants”), or may make use of personal information, the users maybe provided with an opportunity to control whether programs or featurescollect user information (e.g., information about a user's socialnetwork, social actions or activities, profession, a user's preferences,or a user's current geographic location), or to control whether and/orhow to receive content from the content server that may be more relevantto the user. Also, certain data may be treated in one or more waysbefore it is stored or used, so that personal identifiable informationis removed. For example, a user's identity may be treated so that nopersonal identifiable information can be determined for the user, or auser's geographic location may be generalized where geographic locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular geographic location of a user cannot be determined.Thus, the user may have control over how information is collected aboutthe user and/or used.

While several implementations have been described and illustratedherein, a variety of other means and/or structures for performing thefunction and/or obtaining the results and/or one or more of theadvantages described herein may be utilized, and each of such variationsand/or modifications is deemed to be within the scope of theimplementations described herein. More generally, all parameters,dimensions, materials, and configurations described herein are meant tobe exemplary and that the actual parameters, dimensions, materials,and/or configurations will depend upon the specific application orapplications for which the teachings is/are used. Those skilled in theart will recognize, or be able to ascertain using no more than routineexperimentation, many equivalents to the specific implementationsdescribed herein. It is, therefore, to be understood that the foregoingimplementations are presented by way of example only and that, withinthe scope of the appended claims and equivalents thereto,implementations may be practiced otherwise than as specificallydescribed and claimed. Implementations of the present disclosure aredirected to each individual feature, system, article, material, kit,and/or method described herein. In addition, any combination of two ormore such features, systems, articles, materials, kits, and/or methods,if such features, systems, articles, materials, kits, and/or methods arenot mutually inconsistent, is included within the scope of the presentdisclosure.

We claim:
 1. A method implemented by one or more processors, the methodcomprising: connecting, using an automobile computer system, with afirst client device via a wireless communication modality, wherein thefirst client device includes a client automated assistant, and theautomobile computer system comprising an automobile automated assistant;connecting, using the automobile computer system, with a second clientdevice via the wireless communication modality, wherein the secondclient device is separate from the first client device and includesanother client automated assistant; determining, by the automobilecomputer system, that a first action intent request was generated at thefirst client device by an application that is accessible via the firstclient device; determining, by the automobile computer system, that asecond action intent request was generated at the second client deviceby another application that is accessible via the second client device,wherein the second action intent request is different from the firstaction intent request; generating, by the automobile computer system,data indicating a pendency of each action intent request of the firstaction intent request and the second action intent request, wherein thedata is stored at the automobile computer system; and causing, based ongenerating the data, one or more interfaces connected to the automobilecomputer system to provide a notification for each action intent requestof the first action intent request and the second action intent request.2. The method of claim 1, further comprising: processing, for eachaction intent request of the first action intent request and the secondaction intent request, content of each message embodied by each actionintent request.
 3. The method of claim 2, wherein causing the one ormore interfaces connected to the automobile computer system to providethe notification for each action intent request of the first actionintent request and the second action intent request includes: causing anaudio system of the automobile computer system to render audio that isbased on the content of each message.
 4. The method of claim 1, whereingenerating the data indicating the pendency of each action intentrequest includes: generating, by the automobile automated assistant, acorresponding instance of each action intent request of the first actionintent request and the second action intent request.
 5. The method ofclaim 4, further comprising: receiving a user input at the one or moreinterfaces connected to the automobile computer system; and causing, inresponse to receiving the user input, a particular pendency of thenotification associated with the first action intent request to bedismissed at the automobile computer system and the correspondinginstance of the first action intent request to be dismissed at the firstclient device.
 6. The method of claim 5, wherein the user input includesone or more spoken utterances that embody natural language inputprovided by a user.
 7. The method of claim 1, wherein the automobilecomputer system is void of: the application that is accessible via thefirst client device, and the other application that is accessible viathe second client device.
 8. A non-transitory computer readable storagemedium configured to store instructions that, when executed by one ormore processors, cause the one or more processors to perform operationsthat include: connecting, using an automobile computer system, with afirst client device via a wireless communication modality, wherein thefirst client device includes a client automated assistant, and theautomobile computer system comprising an automobile automated assistant;connecting, using the automobile computer system, with a second clientdevice via the wireless communication modality, wherein the secondclient device is separate from the first client device and includesanother client automated assistant; determining, by the automobilecomputer system, that a first action intent request was generated at thefirst client device by an application that is accessible via the firstclient device; determining, by the automobile computer system, that asecond action intent request was generated at the second client deviceby another application that is accessible via the second client device,wherein the second action intent request is different from the firstaction intent request; generating, by the automobile computer system,data indicating a pendency of each action intent request of the firstaction intent request and the second action intent request, wherein thedata is stored at the automobile computer system; and causing, based ongenerating the data, one or more interfaces connected to the automobilecomputer system to provide a notification for each action intent requestof the first action intent request and the second action intent request.9. The non-transitory computer readable storage medium of claim 8,wherein the operations further include: processing, for each actionintent request of the first action intent request and the second actionintent request, content of each message embodied by each action intentrequest.
 10. The non-transitory computer readable storage medium ofclaim 9, wherein causing the one or more interfaces connected to theautomobile computer system to provide the notification for each actionintent request of the first action intent request and the second actionintent request includes: causing an audio system of the automobilecomputer system to render audio that is based on the content of eachmessage.
 11. The non-transitory computer readable storage medium ofclaim 8, wherein generating the data indicating the pendency of eachaction intent request includes: generating, by the automobile automatedassistant, a corresponding instance of each action intent request of thefirst action intent request and the second action intent request. 12.The non-transitory computer readable storage medium of claim 11, whereinthe operations further include: receiving a user input at the one ormore interfaces connected to the automobile computer system; andcausing, in response to receiving the user input, a particular pendencyof the notification associated with the first action intent request tobe dismissed at the automobile computer system and the correspondinginstance of the first action intent request to be dismissed at the firstclient device.
 13. The non-transitory computer readable storage mediumof claim 12, wherein the user input includes one or more spokenutterances that embody natural language input provided by a user. 14.The non-transitory computer readable storage medium of claim 8, whereinthe automobile computer system is void of: the application that isaccessible via the first client device, and the other application thatis accessible via the second client device.
 15. A computing device,comprising: one or more processors, and memory configured to storeinstructions that, when executed by the one or more processors, causethe one or more processors to perform operations that include:connecting, using an automobile computer system, with a first clientdevice via a wireless communication modality, wherein the first clientdevice includes a client automated assistant, and the automobilecomputer system comprising an automobile automated assistant;connecting, using the automobile computer system, with a second clientdevice via the wireless communication modality, wherein the secondclient device is separate from the first client device and includesanother client automated assistant; determining, by the automobilecomputer system, that a first action intent request was generated at thefirst client device by an application that is accessible via the firstclient device; determining, by the automobile computer system, that asecond action intent request was generated at the second client deviceby another application that is accessible via the second client device,wherein the second action intent request is different from the firstaction intent request; generating, by the automobile computer system,data indicating a pendency of each action intent request of the firstaction intent request and the second action intent request, wherein thedata is stored at the automobile computer system; and causing, based ongenerating the data, one or more interfaces connected to the automobilecomputer system to provide a notification for each action intent requestof the first action intent request and the second action intent request.16. The computing device of claim 15, wherein the operations furtherinclude: processing, for each action intent request of the first actionintent request and the second action intent request, content of eachmessage embodied by each action intent request.
 17. The computing deviceof claim 16, wherein causing the one or more interfaces connected to theautomobile computer system to provide the notification for each actionintent request of the first action intent request and the second actionintent request includes: causing an audio system of the automobilecomputer system to render audio that is based on the content of eachmessage.
 18. The computing device of claim 15, wherein generating thedata indicating the pendency of each action intent request includes:generating, by the automobile automated assistant, a correspondinginstance of each action intent request of the first action intentrequest and the second action intent request.
 19. The computing deviceof claim 18, wherein the operations further include: receiving a userinput at the one or more interfaces connected to the automobile computersystem; and causing, in response to receiving the user input, aparticular pendency of the notification associated with the first actionintent request to be dismissed at the automobile computer system and thecorresponding instance of the first action intent request to bedismissed at the first client device.
 20. The computing device of claim15, wherein the automobile computer system is void of: the applicationthat is accessible via the first client device, and the otherapplication that is accessible via the second client device.